Managing monitored conditions in adaptors in a multi-adaptor system

ABSTRACT

Provided are a method, system, and computer program product for managing monitored conditions in adaptors. An adaptor detects a condition comprising one of a plurality of monitored conditions and determines whether the detected condition is indicated on a recent condition list indicating conditions detected at the adaptors. The adaptor communicates the detected condition to cause the detected condition to be included in the recent condition list available at the adaptors in response to determining that the detected condition is not indicated in the recent condition list. Further, a system receives from one of the adaptors indication of a detected condition comprising one of a plurality of monitored conditions that is not indicated on a recent condition list. The received indicated condition is added to the recent condition list to produce an updated recent condition list. Transmission is caused of the updated recent condition list to the adaptors.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a computer program product, system, andmethod for determining priorities for managing monitored conditions inadaptors in a multi-adaptor system.

2. Description of the Related Art

In a high availability multi-adaptor system, the system may providemultiple paths to connected hosts through ports in the multipleadaptors. The system may include one or more processors, such as in asymmetrical multi-processing (SMP) system, to manage the multipleadaptors. If the adaptors detect conditions and errors, then the systemneeds to capture data on the conditions to troubleshoot. Error andcondition recovery operations may interfere with host Input/Output (I/O)operations because host I/O may be quiesced during the conditionrecovery operations.

If the same condition occurs at multiple adaptors, then the multipleadaptors may each independently attempt to capture data and performcondition recovery operations which may cause each adaptor to reset orquiesce I/O with the connected hosts. If all adaptors used by a host toconnect to the server are independently performing data capture andrecovery operations, then the host may lose connection to the server.

In current systems, each adaptor may keep track of conditions that haveoccurred before to avoid performing multiple recovery and data gatheringoperations for conditions that repeatedly occur.

There is a need in the art for improved techniques for managing detectedconditions at adaptors in a multi-adaptor system.

SUMMARY

Provided are a method, system, and computer program product for managingmonitored conditions in adaptors. An adaptor detects a conditioncomprising one of a plurality of monitored conditions and determineswhether the detected condition is indicated on a recent condition listindicating conditions detected at the adaptors. The adaptor communicatesthe detected condition to cause the detected condition to be included inthe recent condition list available at the adaptors in response todetermining that the detected condition is not indicated in the recentcondition list.

In a further embodiment, a system manages conditions in adaptors in thesystem connected to at least one host through the adaptors. Indicationis received from one of the adaptors of a detected condition comprisingone of a plurality of monitored conditions that is not indicated on arecent condition list. The received indicated condition is added to therecent condition list to produce an updated recent condition list.Transmission is caused of the updated recent condition list to theadaptors.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a computing environment in which embodiments areimplemented.

FIG. 2 illustrates an embodiment of a condition list entry in the recentcondition list.

FIG. 3 illustrates an embodiment of operations performed by an adaptorwhen detecting a monitored condition.

FIG. 4 illustrates an embodiment of operations performed by a processorreceiving indication of an adaptor detecting a monitored condition.

FIG. 5 an implementation of a computer/server node in the networkcomputing environment.

DETAILED DESCRIPTION

Described embodiments provide techniques to manage detected conditionsoccurring at adaptors in a multi-adaptor system to avoid performing datacapture or recovery operations every time a monitored condition isdetected that would disrupt communication with attached hosts. With thedescribed embodiments, upon the first occurrence of a detectedcondition, the condition is indicated in a recent condition list anddata capture and recovery operations are performed, even if they maydisrupt communication between that adaptor and the host. Upon subsequentoccurrences of the condition on any of the adaptors, if the detectedcondition is indicated on the recent condition list, then the conditionis logged and control returned to the caller to handle recovery from thecondition. In this way, execution of multiple disruptive conditionrecovery operations, such as data capture, performed for the samedetected condition is avoided.

FIG. 1 illustrates an embodiment of a computing environment having aserver 2 including one or more processors 4 a, 4 b, such as symmetricalmultiple processing (SMP) processors, that communicate with adaptors 6a, 6 b, 6 c over a bus 8. The adaptors 6 a, 6 b, 6 c have ports toconnect to hosts 10 over a network 12. The adaptors 6 a, 6 b, 6 c mayprovide multiple paths 26 a, 26 b, 26 c to communicate with one or morehosts 10 over the network 12. Each processor 4 a, 4 b may manage adifferent group of adaptors 6 a, 6 b, 6 c.

Although a specific number of instances of items, such as the server 2,processors 4 a, 4 b, adaptors 6 a, 6 b, 6 c, host 10 and network 12 areshown, there may be more or fewer instances of these described elements.

Each processor 4 a, 4 b includes an adaptor manager 14 to managecommunication and use of the adaptors 6 a, 6 b, 6 c to communicate overthe network 12. Each adaptor 6 a, 6 b, 6 c may include a processor 16and a memory 18 including program components and data structuresprocessed and executed by the processor 16. The memory 18 includesmonitored conditions 20, a condition monitor 22 program, a recentcondition list 24 indicating recent monitored conditions detected by thecondition monitor 22, and a condition log 28 to log information onconditions detected that are included on the recent condition list 24.In an alternative embodiment, the components of the adaptors 6 a, 6 b, 6c may be implemented with hardware logic, such as in one moreApplication Specific Integrated Circuits (ASICs).

The monitored conditions 20 may comprise conditions the adaptors 6 a, 6b, 6 c detect when processing commands or data from the hosts 10 or froma caller within the server 2, such as one of the processors 4 a, 4 b oranother component. For instance, the adaptor 6 a, 6 b, 6 c may detect anerror condition when processing a sequence of commands from a caller ora sequence of packets that result in a path or communication failure.The monitored conditions 20 may result typically in the adaptors 6 a, 6b, 6 c performing a data capture as well as recovery operation, whichmay disrupt and disconnect the path 26 a, 26 b, 26 c provided by theadaptor 6 a, 6 b, 6 c to the host 10.

The server 2 may comprise a server class enterprise computing devicecapable of servicing requests from multiple connected hosts 10. Thehosts 10 may comprise a desktop computer, server, host, portablecomputing device, such as a smart phone, tablet computing device,telephony device, laptop computer, portable device capable of beingmounted in an automobile, etc. The memory 18 may comprise solid statestorage devices (e.g., EEPROM (Electrically Erasable ProgrammableRead-Only Memory), flash memory, flash disk, Solid State Devices (SSD),storage-class memory (SCM)), electronic memory, etc. The network 12 maycomprise a local area network (LAN), storage area network (SAN), widearea network (WAN), a wireless network, the Internet, etc. The network12 may include wireless network routers and may be part of a cloudcomputing model.

FIG. 2 illustrates an embodiment of a recent condition list 24 entry 50as including a condition code 52 and a caller 54, e.g., host 10 orserver 2 component, that produced the data or commands that resulted inthe adaptor 6 a, 6 b, 6 c realizing the condition 52. Thus, when thecondition monitor 22 detects the occurrence of a condition on themonitored conditions 20 list, an entry 50 is added to the recentcondition list 24 identifying the detected condition code 52 and thecaller 54 that initiated the detected condition.

FIG. 3 illustrates an embodiment of operations performed by thecondition monitor 22 in the adaptors 6 a, 6 b, 6 c when detecting amonitored error condition indicated in the monitored conditions 20 list.Upon detecting (at block 100) the monitored condition, the conditionmonitor 22 determines (at block 102) whether the detected condition isindicated on the recent condition list 24. If not, then the conditionmonitor 22 may communicate (at block 104) the detected condition tocause the detected condition to be included in the recent condition list24 available at the adaptors 6 a, 6 b, 6 c. The condition monitor 22 maygather (at block 106) information on the detected conditioned for errorrecovery purposes and initiate (at block 108) a condition recoveryoperation. The condition recovery operation may cause the path 26 a, 26b, 26 c provided by the adaptor 6 a, 6 b, 6 c detecting the condition todisconnect from the host 10.

If (at block 102) the detected condition is indicated on the recentcondition list 24, then the condition monitor 22 logs (at block 110) thedetected condition in the condition log 28 and returns (at block 112)control to the caller to the adaptor 6 a, 6 b, 6 c that resulted in thedetected condition. The caller may then perform error handling for thecondition detected by the adaptor 6 a, 6 b, 6 c. The fact that thecondition has reoccurred on the same or different adaptors may indicatethat the error is originating from the caller and thus needs to behandled by the caller.

With the operations of FIG. 3, the adaptor 6 a, 6 b, 6 c detecting acondition that has already been detected at any of the adaptors 6 a, 6b, 6 c, as indicated in the recent condition list 24, does not causedata capture or recovery operations that could result in the path 26 a,27 b, 26 c provided by the adaptor 6 a, 6 b, 6 c from disconnecting tothe host 10. Instead, after detecting a condition that has alreadyoccurred on one of the adaptors 6 a, 6 b, 6 c, the occurrence of thecondition is logged and control returns to the caller to proceed withoutdisrupting the host paths 26 a, 26 b, 26 c. Further, with describedembodiments, because the recent condition list 24 is shared among theadaptors 6 a, 6 b, 6 c, the detection of a condition on one adaptor 6 a,6 b, 6 c that has been detected on any of the adaptors would result inthe condition being logged at block 110 in FIG. 3. This ensures that thesame detected condition detected at all of the adaptors 6 a, 6 b, 6 cproviding paths 26 a, 26 b, 26 c to the host 10 does not cause each ofthe adaptors 6 a, 6 b, 6 c to go into recovery and data capture mode soas to disrupt host 10 access to the server 2.

In an embodiment, where the condition list entry 50 indicates both thecondition code 52 and caller 54, the determination of whether thedetected condition is on the recent condition list 24 involves checkingboth the condition and the caller that initiated the detected condition.In this way, a match between a detected condition and the recentcondition list 24 would not occur for a detected condition fromdifferent callers. In alternative embodiments, the recent condition list24 may only indicate the condition 52 and not the caller 54, so that onedetected condition is indicated on the recent condition list 24 forconditions detected from different callers.

FIG. 4 illustrates an embodiment of operations performed by the adaptormanager 14 a, implemented in the processors 4 a, 4 b, to processcondition situations at the adaptors 6 a, 6 b, 6 c. Upon receiving (atblock 130) indication of a detected condition from one of the adaptors 6a, 6 b, 6 c, the adaptor manager 14 adds (at block 132) an entry 50(FIG. 2) for the received indicated condition to the recent conditionlist 24 to produce an updated recent condition list. The adaptor manager14 then causes (at block 134) the transmission of the updated recentcondition list to the adaptors 6 a, 6 b, 6 c to store and maintain asthe recent condition list 24. Further, in a multi-processor system,where additional processors may manage additional adaptors, the adaptormanager 14 may send (at block 136) a message to additional processors 4a, 4 b in the server 2 with the updated recent condition list, whereinthe additional processors forward the updated recent condition list toadaptors they manage.

In one embodiment, the adaptor manager 14 may cause the transmission ofthe updated recent condition list to the adaptors by sending the updatedrecent condition list directly to all the adaptors 6 a, 6 b, 6 c. In analternative embodiment, the adaptor manager 14 may cause thetransmission by sending the updated recent condition list to the adaptor6 a, 6 b, 6 c that sent indication of the detected condition so that theadaptor 6 a, 6 b, 6 c detecting the condition would then propagate theupdated recent condition list to the adaptors 6 a, 6 b, 6 c on anotherprocessor, e.g., 4 b. In a further embodiment, the adaptor manager 14may send the updated recent condition list to the other set of adaptors6 a, 6 b, 6 c, on the same and/or another processor 4 a, 4 b, thatperforms an adaptor cold start, e.g., an Initial Microcode Load (IML),cold boot, code load, etc. In a yet further embodiment, if an adaptor 6a, 6 b, 6 c performs a warm start, such as the result of the conditionrecovery operation, then the adaptor manager 14 will forward the updatedrecent condition list 24 to the restarting adaptor 6 a, 6 b, 6 c andthen the restarting adaptor will send the list to all other adaptorsowned by the processor 4 a, 4 b managing the restarting adaptor. Yetfurther, the adaptor manager 14 may send the updated recent conditionlist 24 to a new adaptor that is added to the server 2 when the newadaptor is initialized.

In one embodiment, the adaptor manager 14 may periodically send acommand to the adaptors 6 a, 6 b, 6 c to clear the recent condition list24 to be empty with no condition list entries 50. The adaptor manager 14may send the command to clear the recent condition list 24 afterexpiration of a time period, e.g., 24 hours, or in response to an eventor condition.

Described embodiments provide techniques to manage detected conditionsoccurring at adaptors 6 a, 6 b, 6 c in a multi-adaptor system to avoidperforming data condition recovery operations, such as data capture,every time a monitored condition is detected that would disruptcommunication with attached hosts. With the described embodiments, uponthe first occurrence of a detected condition, the condition is indicatedin a recent condition list and error recovery performed. Upon subsequentoccurrences of the condition on any of the adaptors, if the detectedcondition is indicated on the recent condition list, then the conditionis logged and control returned to the caller to handle error recovery.In this way, execution of multiple disruptive condition recoveryoperations performed for the same detected condition that could causeall the adaptors to independently disconnect from the host 10 isavoided.

FIG. 5 illustrates an embodiment of a computing node or computer 302 inthe network 12 which may comprise an implementation of the server 2, theprocessors 4 a, 4 b, the adaptors 6 a, 6 b, 6 c, and the hosts 10.Computer 302 is only one example of a computing node and is not intendedto suggest any limitation as to the scope of use or functionality ofembodiments of the invention described herein. Regardless, computingnode 302 is capable of being implemented and/or performing any of thefunctionality set forth hereinabove.

The computer 302 is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with computer system/server302 include, but are not limited to, personal computer systems, servercomputer systems, thin sources, thick sources, handheld or laptopdevices, multiprocessor systems, microprocessor-based systems, set topboxes, programmable consumer electronics, network PCs, minicomputersystems, mainframe computer systems, and distributed cloud computingenvironments that include any of the above systems or devices, and thelike.

Computer 302 may be described in the general context of computer systemexecutable instructions, such as program modules, being executed by acomputer system. Generally, program modules may include routines,programs, objects, components, logic, data structures, and so on thatperform particular tasks or implement particular abstract data types.Computer system 302 may be practiced in cloud computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed cloud computingenvironment, program modules may be located in both local and remotecomputer system storage media including memory storage devices.

As shown in FIG. 5, computer 302 is shown in the form of ageneral-purpose computing device. The components of computer 302 mayinclude, but are not limited to, one or more processors or processingunits 304, a system memory 306, and a bus 308 that couples varioussystem components including system memory 306 to processor 304.

Bus 308 represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronics Standards Association (VESA) local bus, andPeripheral Component Interconnects (PCI) bus.

Computer 302 typically includes a variety of computer system readablemedia. Such media may be any available media that is accessible bycomputer system/server 302, and it includes both volatile andnon-volatile media, removable and non-removable media.

System memory 306 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 310 and/or cachememory 312. Computer system/server 302 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 313 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 308 by one or more datamedia interfaces. As will be further depicted and described below,memory 306 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 314, having a set (at least one) of program modules 316,may be stored in memory 306 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 316 generally carry out the functionsand/or methodologies of embodiments of the invention as describedherein.

Computer 302 may also communicate with one or more external devices 318such as a keyboard, a pointing device, a display 320, etc.; one or moredevices that enable a user to interact with computer system/server 12;and/or any devices (e.g., network card, modem, etc.) that enablecomputer system/server 302 to communicate with one or more othercomputing devices. Such communication can occur via Input/Output (I/O)interfaces 322. Still yet, computer system/server 302 can communicatewith one or more networks such as a local area network (LAN), a generalwide area network (WAN), and/or a public network (e.g., the Internet)via network adapter 324. As depicted, network adapter 324 communicateswith the other components of computer system/server 302 via bus 308. Itshould be understood that although not shown, other hardware and/orsoftware components could be used in conjunction with computersystem/server 302. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

The described operations may be implemented as a method, apparatus orcomputer program product using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. Accordingly, aspects of the embodiments may take the form of anentirely hardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,aspects of the embodiments may take the form of a computer programproduct embodied in one or more computer readable medium(s) havingcomputer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

Further, although process steps, method steps, algorithms or the likemay be described in a sequential order, such processes, methods andalgorithms may be configured to work in alternate orders. In otherwords, any sequence or order of steps that may be described does notnecessarily indicate a requirement that the steps be performed in thatorder. The steps of processes described herein may be performed in anyorder practical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

The illustrated operations of the figures show certain events occurringin a certain order. In alternative embodiments, certain operations maybe performed in a different order, modified or removed. Moreover, stepsmay be added to the above described logic and still conform to thedescribed embodiments. Further, operations described herein may occursequentially or certain operations may be processed in parallel. Yetfurther, operations may be performed by a single processing unit or bydistributed processing units.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims herein after appended.

What is claimed is:
 1. A computer program product for managingconditions in an adaptor in a system having a plurality of adaptors toconnect to at least one host, the computer program product comprising acomputer readable storage medium in one of the adaptors having computerreadable program code embodied therein that executes to performoperations, the operations comprising: detecting a condition comprisingone of a plurality of monitored conditions; determining whether thedetected condition is indicated on a recent condition list indicatingconditions detected at the adaptors; and communicating the detectedcondition to cause the detected condition to be included in the recentcondition list available at the adaptors in response to determining thatthe detected condition is not indicated in the recent condition list. 2.The computer program product of claim 1, wherein the operations furthercomprise: in response to determining that the detected condition is notindicated in the recent condition list, performing: gatheringinformation on the detected condition; and initiating a conditionrecovery operation.
 3. The computer program product of claim 2, whereinthe initiated condition recovery operation causes the adaptor todisconnect from the at least one attached host.
 4. The computer programproduct of claim 1, wherein the operations performed in response todetermining that the condition is indicated in the recent condition listcomprises: logging the detected condition in an information log; andreturning control to a caller of the adaptor that resulted in thedetected condition.
 5. The computer program product of claim 1, whereincommunicating the detected condition comprises: adding the detectedcondition to the recent condition list to produce an updated recentcondition list; and transmitting the updated recent condition list toother adaptors of the plurality of the adaptors.
 6. The computer programproduct of claim 1, wherein communicating the detected conditioncomprises: communicating the detected condition to a processor in thesystem to cause the processor to transmit an updated recent conditionlist to the adaptors in the system.
 7. The computer program product ofclaim 1, wherein the operations further comprise: periodicallyinvalidating the recent condition list to replace with a new recentcondition list having no indicated conditions.
 8. The computer programproduct of claim 1, wherein communicating the detected conditioncomprises: communicating the detected condition to a processor in thesystem; receiving from the processor an updated recent condition listindicating the detected condition; and transmitting the updated recentcondition list to other of the adaptors.
 9. A computer program productfor managing conditions in adaptors in a system connected to at leastone host through the adaptors, the computer program product comprising acomputer readable storage medium having computer readable program codeembodied therein that executes to perform operations, the operationscomprising: receiving indication from one of the adaptors of a detectedcondition comprising one of a plurality of monitored conditions that isnot indicated on a recent condition list; adding the received indicatedcondition to the recent condition list to produce an updated recentcondition list; and causing a transmission of the updated recentcondition list to the adaptors.
 10. The computer program product ofclaim 9, wherein the operations further comprise: periodically causingthe adaptors to reset their recent condition list to include no entriesof detected conditions.
 11. The computer program product of claim 9,wherein the operations further comprise: detecting a restart of one ofthe adaptors; and sending the updated recent condition list to therestarting adaptor to use.
 12. The computer program product of claim 9,wherein the operations further comprise: detecting a new adaptor addedto the system; and sending the updated recent condition list to the newadaptor to use.
 13. The computer program product of claim 9, wherein theoperations further comprise: sending a message to additional processorsin the system with the updated recent condition list, wherein theprocessors forward the updated recent condition list to adaptors theymanage.
 14. An adaptor in a system having a plurality of adaptorsconnected to at least one host, comprising: a computer readable storagemedium including a condition monitor program executed to performoperations, the operations comprising detecting a condition comprisingone of a plurality of monitored conditions; determining whether thedetected condition is indicated on a recent condition list indicatingconditions detected at the adaptors; and communicating the detectedcondition to cause the detected condition to be included in the recentcondition list available at the adaptors in response to determining thatthe detected condition is not indicated in the recent condition list.15. The adaptor of claim 14, wherein the operations further comprise: inresponse to determining that the detected condition is not indicated inthe recent condition list, performing: gathering information on thedetected condition; and initiating a condition recovery operation. 16.The adaptor of claim 15, wherein the initiated condition recoveryoperation causes the adaptor to disconnect from the at least oneattached host.
 17. The adaptor of claim 14, wherein communicating thedetected condition comprises: adding the detected condition to therecent condition list to produce an updated recent condition list; andtransmitting the updated recent condition list to other adaptors of theplurality of the adaptors.
 18. A system for managing conditions inadaptors connected to at least one host through the adaptors,comprising: a processor; and a computer readable storage medium havingan adaptor manager executed by the processor to perform operations, theoperations comprising: receiving indication from one of the adaptors ofa detected condition comprising one of a plurality of monitoredconditions that is not indicated on a recent condition list; adding thereceived indicated condition to the recent condition list to produce anupdated recent condition list; and causing a transmission of the updatedrecent condition list to the adaptors.
 19. The system of claim 18,wherein the operations further comprise: detecting a restart of one ofthe adaptors; and sending the updated recent condition list to therestarting adaptor to use.
 20. The system of claim 18, wherein theoperations further comprise: sending a message to additional processorsin the system with the updated recent condition list, wherein theprocessors forward the updated recent condition list to adaptors theymanage.
 21. A method for managing conditions in an adaptor in a systemhaving a plurality of adaptors to connect to at least one host,comprising: detecting a condition comprising one of a plurality ofmonitored conditions; determining whether the detected condition isindicated on a recent condition list indicating conditions detected atthe adaptors; and communicating the detected condition to cause thedetected condition to be included in the recent condition list availableat the adaptors in response to determining that the detected conditionis not indicated in the recent condition list.
 22. The method of claim21, wherein the operations further comprise: in response to determiningthat the detected condition is not indicated in the recent conditionlist, performing: gathering information on the detected condition; andinitiating a condition recovery operation.
 23. The method of claim 22,wherein the initiated condition recovery operation causes the adaptor todisconnect from the at least one attached host.
 24. The method of claim21, wherein communicating the detected condition comprises: adding thedetected condition to the recent condition list to produce an updatedrecent condition list; and transmitting the updated recent conditionlist to other adaptors of the plurality of the adaptors.
 25. A methodfor managing conditions in adaptors in a system connected to at leastone host through the adaptors, comprising: receiving indication from oneof the adaptors of a detected condition comprising one of a plurality ofmonitored conditions that is not indicated on a recent condition list;adding the received indicated condition to the recent condition list toproduce an updated recent condition list; and causing a transmission ofthe updated recent condition list to the adaptors.
 26. The method ofclaim 25, further comprising: detecting a restart of one of theadaptors; and sending the updated recent condition list to therestarting adaptor to use.
 27. The method of claim 25, furthercomprising: sending a message to additional processors in the systemwith the updated recent condition list, wherein the processors forwardthe updated recent condition list to adaptors they manage.